NASA Mission Management Team–Debris Assessment Team relationship

The relationship between NASA’s Mission Management Team (MMT) and Debris Assessment Team (DAT) during the Columbia mission became a consequential divide between engineers trying to characterize an uncertain hazard and managers who treated the available analysis as sufficient reassurance. The DAT’s warnings did not reach the MMT with their full qualifications, and the MMT’s meetings left little room to test or challenge the conclusions presented. In the book’s account, the failure lay not only in what the teams knew, but in how information and judgment moved between them.

Two teams, unequal roles

During mission STS-107, the twenty-eighth flight of the space shuttle Columbia, the DAT consisted of engineers from NASA, Boeing, and Lockheed Martin. After a large piece of foam broke away from the left bipod area of the external fuel tank during ascent and struck the shuttle’s left wing, the DAT spent much of the following five days assessing what the impact might have done. The MMT, by contrast, was the management body considering the mission’s status and what, if anything, should be done. Linda Ham led it; Don McCormack served as an unofficial liaison between the teams.

The evidence available to the DAT was incomplete from the start. Cameras tracking the launch had not produced a clear picture of the impact, leaving the engineers uncertain about the size of the foam and the precise damage to the wing. A request for on-orbit images had been made by January 21, but the images had not been approved. The DAT therefore estimated the foam’s size and speed, then used an algorithm called Crater to predict how deeply an object of that size and speed might penetrate the shuttle’s thermal-protection tiles. The assessment depended on estimates and a tool whose limitations would become central to the communication between the groups.

The first briefing and a foreclosed question

On January 21, an hour before the MMT’s second teleconference since Columbia’s January 16 launch, McCormack had been briefed by DAT members. They had reached no conclusion, but had made clear that there was reason for concern. During the MMT meeting, however, the foam strike did not come up until about two-thirds of the way through the discussion, after topics including a jammed camera, scientific experiments, and a leaky water separator. When Ham asked for an update, McCormack said people were investigating possible damage and possible repairs. He also mentioned that a similar strike on an earlier flight had caused “fairly significant damage.”

Ham responded that she did not think there was much the team could do and that the strike was therefore not really a factor during the flight. The book describes this as more than a judgment about the available options: Ham had already decided the strike was inconsequential, and made that decision for the rest of the meeting as well. The MMT had not yet heard the DAT’s detailed concerns. McCormack could have outlined potential consequences and discussed what earlier debris strikes had shown, but the conversation moved on instead. The DAT’s uncertainty entered the management discussion without becoming a question the group examined together.

The January 24 findings

On January 24, the DAT engineers met again with McCormack to present the results of their foam-strike study. The briefing room was so crowded that some engineers had to stand in the hallway, a sign within the account of how concerned people were. The DAT offered five possible scenarios. Its conclusion was that the shuttle was likely safe, but it qualified that conclusion sharply: the analysis was profoundly limited by the tools available and by the lack of good information. Because the MMT had not approved on-orbit images, the engineers did not know exactly where the foam had struck. Crater, meanwhile, had been designed to assess debris hundreds of times smaller than the object that hit Columbia, so its results could not be treated as dependable for this case. The engineers stressed uncertainty; NASA management focused on the likely-safe conclusion.

An hour after the briefing, the MMT met. McCormack told the group that the analysis showed the potential for significant damage, but that thermal analysis did not indicate a possible burn-through. He also said that substantial uncertainty remained about the debris’s size, where it had struck, and its angle of incidence. Ham recast the discussion as a sequence of reassuring propositions, asking whether no burn-through meant no catastrophic damage and only localized heating that would require tile replacement. McCormack replied that the team did not yet see a safety-of-flight issue. Ham then asked whether there was no issue for the mission and nothing that needed to be done differently, apart from a possible turnaround issue.

After a short exchange involving Ham, McCormack, and Calvin Schomburg, another participant said he had not been able to hear McCormack. Ham summarized the exchange as meaning that he did not believe there was burn-through or a safety-of-flight issue, only a possible turnaround concern, and asked whether there were questions. The meeting ended without a member asking to see the DAT study or probing the uncertainties McCormack had named. The account stresses that the engineers’ cautious qualification and the managers’ reassuring restatement were not equivalent: the latter made an uncertain analysis sound like a settled finding.

How warnings lost force

The MMT’s handling of the DAT’s work reflected both a failure to transmit information fully and a failure to test what had been transmitted. When McCormack summarized the study, he did not include the supporting analysis or explain whether the DAT itself was divided about its conclusions. Yet the MMT did not ask for that analysis, request clarification, or invite further discussion. Ham’s brisk summary—turning the absence of indicated burn-through into the absence of catastrophic damage—helped close off the space in which questions might have been asked. The book notes that her closing invitation for questions functioned less as an opening for debate than as a cue that discussion was finished.

The relationship was also shaped by NASA’s hierarchy. Although the DAT engineers had serious concerns from the beginning, and insisted that images of the Orbiter’s wing were needed for an informed assessment, those concerns did not receive a serious hearing from the MMT. The team’s discussions were at once overstructured and insufficiently structured: much of the exchange consisted of Ham asking a question and another person answering, while no process ensured that other members commented on the issues. The contrast matters. A meeting can have a leader and a sequence of questions without creating a real forum for collective analysis; here, the structure organized the exchange around the leader’s framing rather than around the range of evidence and judgment available.

The DAT’s request for images was not the only lost opportunity. The team had been urged on multiple occasions to collect the information needed to make a reasonable safety estimate, and members of the MMT’s leadership raised the possibility that the damage could be severe. The book argues that the MMT could have made different choices that might have improved the crew’s chances of survival. It also cautions against treating the team in isolation from NASA’s wider institutional and cultural problems. Even so, those broader failures do not erase the specific interaction: the engineers’ incomplete evidence and expressed concern were not turned into a management decision to investigate further.

Dissent and the cost of premature agreement

The book uses the MMT–DAT relationship to show why merely transmitting information is not enough. A group must also have ways to aggregate judgments and make room for disagreement. In the Columbia case, the DAT’s technical reservations reached the management process in a diminished form, while the MMT’s apparent agreement was never stress-tested. Starting from the conclusion that the strike was not consequential shaped how later information was interpreted, making qualifications easier to overlook and reassuring phrases easier to repeat.

The account contrasts this with research on small-group decisions in which even a minority viewpoint can make a group’s reasoning more rigorous. A dissenting position need not ultimately prove correct to be useful: its presence forces the majority to examine its assumptions more carefully. The author suggests that a single advocate pressing the possibility that the foam had seriously damaged the wing might have changed the MMT’s conclusion. That counterfactual is not presented as a certainty, but it clarifies what the group lacked: not simply more technical expertise, but an organized encounter between competing interpretations of the evidence.

The relationship’s significance, then, lies in the gap between having specialized knowledge and making that knowledge consequential. The DAT investigated the strike, identified the limits of its methods, and sought better evidence. The MMT had the authority to decide what the mission would do, but its discussion did not preserve the DAT’s uncertainty as a live issue. In the book’s broader argument about groups and organizations, the episode is a warning that expertise and information can remain locally available yet fail collectively when hierarchy, premature certainty, and the absence of dissent prevent them from shaping a decision.